Writes a trace message to indicate that a given section of code has begun. Must be followed by a call to {@link ATrace_endAsyncSection} with the same methodName and cookie. Unlike {@link ATrace_beginSection} and {@link ATrace_endSection}, asynchronous events do not need to be nested. The name and cookie used to begin an event must be used to end it.
Writes a tracing message to indicate that the given section of code has begun. This call must be followed by a corresponding call to {@link ATrace_endSection} on the same thread.
Writes a trace message to indicate that the current method has ended. Must be called exactly once for each call to {@link ATrace_beginAsyncSection} using the same name and cookie.
Writes a tracing message to indicate that a given section of code has ended. This call must be preceeded by a corresponding call to {@link ATrace_beginSection} on the same thread. Calling this method will mark the end of the most recently begun section of code, so care must be taken to ensure that {@link ATrace_beginSection}/{@link ATrace_endSection} pairs are properly nested and called from the same thread.
Returns true if tracing is enabled. Use this to avoid expensive computation only necessary when tracing is enabled.
Writes trace message to indicate the value of a given counter.
@file trace.h @brief Writes trace events to the system trace buffer.
These trace events can be collected and visualized using the Systrace tool. For information about using the Systrace tool, read <a href="https://developer.android.com/studio/profile/systrace.html">Analyzing UI Performance with Systrace</a>.
Available since API level 23.